Ubuntu 16.04
Sponsored Link

Redis : Use Redis Benchmark
2016/09/08
 
It's possible to run a benchmark test with a tool included in Redis package.
[1] Use redis-benchmark tool like follows.
For others, there are some options to specify number of requests and so on, see "redis-benchmark --help".
root@dlp:~#
redis-benchmark -h 10.0.0.30 -p 6379

====== PING_INLINE ======
  100000 requests completed in 1.26 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

98.30% <= 1 milliseconds
99.90% <= 2 milliseconds
99.94% <= 3 milliseconds
99.95% <= 4 milliseconds
100.00% <= 4 milliseconds
79491.26 requests per second

====== PING_BULK ======
  100000 requests completed in 1.28 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

99.99% <= 1 milliseconds
100.00% <= 1 milliseconds
77942.32 requests per second

====== SET ======
  100000 requests completed in 1.29 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

100.00% <= 0 milliseconds
77579.52 requests per second

====== GET ======
  100000 requests completed in 1.28 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

100.00% <= 0 milliseconds
78186.08 requests per second

====== INCR ======
  100000 requests completed in 1.29 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

100.00% <= 1 milliseconds
77519.38 requests per second

====== LPUSH ======
  100000 requests completed in 1.27 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

100.00% <= 0 milliseconds
78678.20 requests per second

====== LPOP ======
  100000 requests completed in 1.27 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

100.00% <= 0 milliseconds
78492.93 requests per second

====== SADD ======
  100000 requests completed in 1.28 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

100.00% <= 0 milliseconds
78064.01 requests per second

====== SPOP ======
  100000 requests completed in 1.28 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

100.00% <= 0 milliseconds
78003.12 requests per second

====== LPUSH (needed to benchmark LRANGE) ======
  100000 requests completed in 1.32 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

99.67% <= 1 milliseconds
99.97% <= 2 milliseconds
100.00% <= 2 milliseconds
75987.84 requests per second

====== LRANGE_100 (first 100 elements) ======
  100000 requests completed in 1.32 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

100.00% <= 1 milliseconds
75930.14 requests per second

====== LRANGE_300 (first 300 elements) ======
  100000 requests completed in 1.32 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

99.96% <= 1 milliseconds
100.00% <= 1 milliseconds
75987.84 requests per second

====== LRANGE_500 (first 450 elements) ======
  100000 requests completed in 1.26 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

99.97% <= 1 milliseconds
100.00% <= 1 milliseconds
79113.92 requests per second

====== LRANGE_600 (first 600 elements) ======
  100000 requests completed in 1.22 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

99.97% <= 2 milliseconds
100.00% <= 2 milliseconds
81900.09 requests per second

====== MSET (10 keys) ======
  100000 requests completed in 1.23 seconds
  50 parallel clients
  3 bytes payload
  keep alive: 1

99.80% <= 1 milliseconds
99.95% <= 2 milliseconds
100.00% <= 2 milliseconds
81433.22 requests per second
 
Tweet